Skip to content

fix(website): serve blog pages correctly, add serving regression test - #323

Merged
vsilent merged 35 commits into
devfrom
fix/revert-breaking-deps
Nov 5, 2026
Merged

vsilent merged 35 commits into
devfrom
fix/revert-breaking-deps

Conversation

@vsilent

@vsilent vsilent commented Nov 5, 2026

Copy link
Copy Markdown
Collaborator

Problem

serve -s dist in the Dockerfile runs SPA mode, which rewrites every blog path to the landing page. stacker.my/blog and its article URLs were broken.

Fix

  • Remove -s flag from serve in Dockerfile
  • Add website/tests/serving.mjs regression test
  • Run test in CI before Docker build
  • Document fix in CHANGELOG.md

dependabot Bot and others added 30 commits April 23, 2026 01:27
Bumps [openssl](https://github.com/rust-openssl/rust-openssl) from 0.10.76 to 0.10.78.
- [Release notes](https://github.com/rust-openssl/rust-openssl/releases)
- [Commits](rust-openssl/rust-openssl@openssl-v0.10.76...openssl-v0.10.78)

---
updated-dependencies:
- dependency-name: openssl
  dependency-version: 0.10.78
  dependency-type: indirect
...

Signed-off-by: dependabot[bot] <support@github.com>
Bumps [thin-vec](https://github.com/mozilla/thin-vec) from 0.2.15 to 0.2.18.
- [Changelog](https://github.com/mozilla/thin-vec/blob/main/RELEASES.md)
- [Commits](https://github.com/mozilla/thin-vec/commits)

---
updated-dependencies:
- dependency-name: thin-vec
  dependency-version: 0.2.16
  dependency-type: indirect
...

Signed-off-by: dependabot[bot] <support@github.com>
Bumps [vitest](https://github.com/vitest-dev/vitest/tree/HEAD/packages/vitest) from 1.6.1 to 3.2.6.
- [Release notes](https://github.com/vitest-dev/vitest/releases)
- [Changelog](https://github.com/vitest-dev/vitest/blob/main/docs/releases.md)
- [Commits](https://github.com/vitest-dev/vitest/commits/v3.2.6/packages/vitest)

---
updated-dependencies:
- dependency-name: vitest
  dependency-version: 3.2.6
  dependency-type: direct:development
...

Signed-off-by: dependabot[bot] <support@github.com>
feat(admin-notifications): mark-all-read proxy + marketplace/bake fixes
Update dependency @types/react to v18.3.31
Update Rust crate derive_builder to 0.20.0
…kfile

Update Rust crate clap_complete to v4.6.10
Update trydirect/stacker Docker tag to v0.3.2
…test-3.2.6

Bump vitest from 1.6.1 to 3.2.6 in /web
chore(deps): Bump openssl from 0.10.76 to 0.10.78
Update Rust crate deadpool-lapin to 0.14.0
vsilent and others added 5 commits October 29, 2026 12:11
Update Rust crate config to 0.15.0
feat(website): add blog section with AI startup hosting article
hmac 0.13, deadpool-lapin 0.14, config 0.15, derive_builder 0.20,
and dialoguer 0.12 have breaking API changes the code is not adapted
to. Revert to the versions dev compiles against:

- hmac 0.13.0 -> 0.12.1 (Hmac::new_from_slice removed in 0.13)
- deadpool-lapin 0.14.0 -> 0.12.1 (create_pool signature changed)
- config 0.15.0 -> 0.13.4
- derive_builder 0.20.0 -> 0.12.0
- dialoguer 0.12 -> 0.11

russh still pulls hmac 0.13 transitively for its own use; the direct
hmac 0.12 dependency keeps the code's imports on the old API.

Also allowlist Cargo.lock checksums in check-staged-secrets.sh.
- Remove -s flag from serve in Dockerfile (SPA mode rewrote all blog
  URLs to the landing page)
- Add website/tests/serving.mjs regression test
- Run test in CI before Docker build
- Document fix in CHANGELOG.md
@vsilent
vsilent merged commit 4e8eff4 into dev Nov 5, 2026
8 of 9 checks passed
@gitguardian

gitguardian Bot commented Nov 5, 2026

Copy link
Copy Markdown

⚠️ GitGuardian has uncovered 2 secrets following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secrets in your pull request
GitGuardian id GitGuardian status Secret Commit Filename
38612145 Triggered Bearer Token 9b165e7 src/cli/generator/compose.rs View secret
38612146 Triggered Redis Server Password 9b165e7 src/cli/generator/compose.rs View secret
🛠 Guidelines to remediate hardcoded secrets
  1. Understand the implications of revoking this secret by investigating where it is used in your code.
  2. Replace and store your secrets safely. Learn here the best practices.
  3. Revoke and rotate these secrets.
  4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider


🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants